home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19971216-19980424
/
000033_news@newsmaster….columbia.edu _Fri Jan 2 10:25:14 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
5KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id KAA10392
for <kermit.misc@watsun.cc.columbia.edu>; Fri, 2 Jan 1998 10:25:14 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id KAA16462
for kermit.misc@watsun; Fri, 2 Jan 1998 10:25:13 -0500 (EST)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: MSDOS Kermit 3.15 bug.
Date: 2 Jan 1998 15:25:11 GMT
Organization: Columbia University
Lines: 79
Message-ID: <68j0sn$hdj$1@apakabar.cc.columbia.edu>
References: <68hst7$r0e$1@goanna.cs.rmit.edu.au>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:8199
In article <68hst7$r0e$1@goanna.cs.rmit.edu.au>,
Ross Irvine <rwi@yallara.cs.rmit.edu.au> wrote:
: I think I have a bug in MSDOS Kermit 3.15 Patch Level 1 (The patch level
: one is the non working ON_EXIT macro I reported). This was also sent to
: kermit-bugs many weeks ago but I haven't heard anything...
:
It's in the queue.
: It seems that using a switch statement anywhere in a script will clear
: the value of any paramaters you have passed to that script. Well the
: first one anyway (\%1).,.
: ...
: As soon as the switch statement has been reached the value of \%1 goes.
: Remove the switch statement from my script allows \%1 to live on until
: the end of the script (as it should).
:
: Has anyone notice that the msdos version of kermit is becomming VERY
: unstable?
:
Version 3.15 was in Beta test for over a year; each Beta release was
announced on our newsgroup and our website. Evidently most people waited
until after it was released to start testing it.
: Something that works on our copy of Kermit 95 (btw when will the gui be
: released for this?)...
:
>From your K95 FAQ.TXT file:
Q: When will Kermit 95 become a full GUI application?
A: A full-GUI release with no console windows for Windows 95 and NT is
expected sometime in 1998. Registered users of Kermit 95 1.1.x will
receive it at no additional cost. Watch the Kermit 95 web page and the
newsgroup, comp.protocols.kermit.misc, and the Windows 95 and NT and OS/2
newsgroups for announcements. It is not yet determined whether there will
be a full-GUI (Presentation Manager) version for OS/2.
In other words, we're still working on it. It is taking a long time.
And remember that, for the most part, it will be exactly what you have now,
but with a different appearance, and a far more labor-intensive mode of
operation :-)
: ... without a problem will send msdos kermit to it's death
: with all sorts of errors "exausted workspace" "text exceeded available
: buffer capicty) and all of suddent shelling to do for no reason.
:
Problems with MS-DOS Kermit or other Kermit software should be reported via
email to kermit-support@columbia.edu (as you have done).. We do our best to
supply workarounds and fix the underlying problems.
Bear in mind that Kermit 95 operates in a virtual memory environment,
generally on PCs that have 16, 32, 64 or more MB of main memory. The amount
of functionality, the sizes of buffers, etc, are practically without limit.
MS-DOS Kermit tries to provide most of the same functionality in a tiny
fraction of the space, which adds an extra level of complexity. Remember,
MS-DOS Kermit must not only fit in 640K, but also must leave room for other
applications in the same 640K.
Several bugs have surfaced in MS-DOS Kermit 3.15 since it was released; the
one you have noticed about "memory exhausted" is not patchable. It can be
worked around, however, by breaking long macros, SWITCH, XIF, WHILE, and FOR
statemants into smaller pieces. The next release, 3.16, will recover more
gracefully from too-long command sequences, but the limits will still be
there.
The problem with SWITCH destroying macro arguments will be fixed too. In the
meantime, work around it by copying the macro argument to another variable
upon entry to the macro.
Although we have not advertised it publicly yet, there is a 3.16 Alpha-test
version in:
http://www.columbia.edu/kermit/test/bin/msk316.zip
It should fix most or all of the bugs you notice. If you find any problems
in it, report them in the usual way.
- Frank